I wouldn't buy it, and I didn't. Here's why...I was looking for a book that was comprehensive, had lots of pictures and diagrams in it, and was worth the price. After thumbing through the book and reading a few pages, I was disappointed to see the huge print and found the content not very enlightening. For what can found in that book and for that price, I would suggest looking at another book. I recently purchased Shotgunning: the art and the science, by Brister. I've found that this book is far more comprehensive and provides better pictures and diagrams of what the author is trying to show--and not for that much more. Without having read the book, this review doesn't carry the same weight as a review of a book that I've read. If you're willing to give this book a try, go for it. But if you're on a tight budget like me, you can find more book for your dollar someplace else.

I have used this book in my reading classes for graduates. It has become an excellent tool in my classroom as well. I have lent it to several teachers to use when questions concerning phonics or methods arrive. It's an excellent resource book to keep close at hand in the classroom.

Everyone is in a feeding frenzy to learn more about Golf's new sensation, Tiger Woods. Jack Clary satisfies this hunger by producing this wonderful picture book outlining Tiger's career from his earliest days to his winning of the 1997 Masters Championship. If you are a follower of Eldrick Woods' career, you won't find anything new in terms of his accomplishments. What then, distinguishes this book from the plethora of texts written about this golf prodigy after his Master's Win?

Clary provides us with outstanding photographs of Tiger along with exciting prose giving us an interpretation of his golfing skills. Of greatest interest is the author's detailed description of Tiger at the Masters. We are taken through round by round of the play. Clary gives a brief summary of what Woods did at each hole. You almost feel as if you are there as our author tells you the story through words augmented with the color photographs. When you walk on the course with Woods, you feel that you are in the presence of a person who will totally change how golf is played.

The Master's description alone is a reason to have this book in your personal library. Clary did an excellent job in bringing you into the game and in enabling you to develop a great appreciation for one of Golf's greatest players.

Comes across a bit like watered down Burroughs, but this writing is interesting because it's so stripped down--acoustic Burroughs--lacking the electrical force of the explosion of images, and rape and plundering of words which typifies Burroughs--but while retaining Burroughs' subject matter.

This first piece in this book however is the exception--"Thanksgiving Day, Nov. 28, 1986"--lays out Burroughs' position on America rather sweetly.

Written in four parts, TWISTED ROADS details the kidnapping of seven-year-old Katrina and the ramifications of that crime. Sexual predator Roy Thornquist was recently released from a mental hospital before kidnapping Katrina as she leaves her school bus. Shockingly, two hospital psychologists had pronounced Thornquist rehabilitated. The combined efforts of the local police and the State Police and the Canadian police track Thornquist result in his capture.

Previously, Thornquist had been suspected in a sixteen-year-old kidnapping case in which the child's body was never found. In the second section of TWISTED ROADS, the victim of the sixteen-year-old crime is at last discovered. Her family struggles with reconciling themselves to the finality of the discovery of their child's body. In the third section, a millionaire forms the vigilante group Warmstorm to rid the world of sexual predators like Thornquist. The forth section proves the horrible consequences of vigilantism.

The four sections of TWISTED ROADS read much like four loosely linked short stories. Unfortunately, TWISTED ROADS falls victim to the flaws of self-publishing, even as it offers powerful food for thought. Ordinarily I do not mention formatting or other technical concerns with a book in my reviews because they do not reflect specifically on the author's writing ability. However, with this self-published novel the uneven margins with an inch and a half at the top of each page is a bit disconcerting, leaving the reader feeling as though the presentation was orchestrated to falsely present a longer book. In addition, unconventional editing choices, such as the use of parenthesis or dashes, may be distracting to readers.

Specifically addressing the content of the novel, the author would have benefited from a writing critique group that focused on "show don't tell" when creating characters and motivation. Much of the book is a series of long paragraphs that describe the events and people, with the unfortunately result of flat characterizations and a lack of tension. Nevertheless, the author presents a timely and deeply philosophical book that examines the conundrums of vigilantism and the flaws of its use. An interesting read, TWISTED ROADS comes recommended.

A reporter at an ultra-liberal Atlanta newspaper and an aide for a Congresswoman who spends her summers helping Fidel Castro harvest his sugar cane crop have teamed up to offer a predictably biased account of the Kaolin Industry in Georgia.You might as well get out your little red book of the sayings of Mao-tse-tung as waste your time on this tripe.

I read this book, and it is basically a condemnation of the kaolin companies and a glorification of their opponents. The author is an environmentalist reporter for the Atlanta Journal and Constitution, which should tell you all you need to know about the book's objectivity.

This book reveals a feudal system still in existence in southern Georgia today. It will infuriate you, whether you live in the state or not. It's a great example of investigative journalism (obviously, the first reviewer works for the Kaolin companies who have been robbing the poor blacks and even the state of Georgia blind for decades!) But be warned, this book will make you angry -- at the abuses, the coverups, the lack of governmental backbone to take on this industry. But maybe if enough of us read this book, something, finally, will change.

I hate to say it, but the entire premise for the hero is just laughable. I couldn't even finish the book because of it. The thought that someone went all the way through four years of vet school, where needles abound (especially in the deep south - heartworm anyone?) could work there way all the way through, only to give it up after graduation, because they can't stand to cause anything any pain (including using needles) is a joke. I just couldn't make myself even start to accept the hero. Needless to say, I didn't make it far through the book, because I just couldn't believe in the hero. The rest of the book's premise is nothing to shout about either. Woman with a daughter by the dead twin brother of the hero, who no-one has ever heard about before, comes to town to steal a kidney from someone in the family. Oh please! I can read (and enjoy) paranormals, but a vet who spooks around needles is just too unbelievable.

Can anyone imagine a small adult female kidnapping and tying up a big hunk?? I could not! The premise of this story was too much of a stretch. Amazing as I found ROAN was a fantastic story! The heroine waffled from one plan to another and all of them were way out in "left field" I have completed all the Benedict books - sorry this one was so disappointing!

I actually found this book to have the most believable plot of the series so far (I have yet to read WADE). Blake does a good job of describing renal disease and the frustration and desperation a mother can feel for a sick child. Being a mother of a child with a genetic disease I could identify with the characters. Having Clay be a twin of the father (which was not a surprise since it is mentioned in the previous book) was the only reliable way to resolve the organ donation issue and it worked well within the plot of the book and the series as a whole. I think you will enjoy this book if you have enjoyed the others in the series.

This is the worst java book I've ever read. The book is unorganized and the content is not suitable for the beginner at all.

The companion CD-ROM is useless.

If the authors would like to publish the new version for JDK 1.2, there will be a lot of works they need to get accomplished.

Simple words from me.... Don't buy this book.

Covers alot of fancy staff but has a great lack of contents. It seems like the author has rushed through the book just to fill it out with the Java 1.1 features and forgot to describe the import basics behind the language. There's now way you're gonna be a Java guru by reading this book!

It is very thorough. Almost everything important about java is in there including JDBC, JNI, Java Beans, Servlets, security management, even the specification of the virtual machine and most is explained well understandble. It is the best java book I ever saw!

This is the worst book I have ever read in my life. Authors would do themselves a favour if they have just written a decent 15 page scientific paper rather than this trash. Even 1 star for this book is too much. What makes it even worse is that stereotypes that these so called PhDs are projecting. These two should be banned from publishing and teaching. If anyone wants the book I wil ship it to you. For free. Otherwise, this is going into the recycling paper bin.

Overall, the book Why Erp? gave a good description on implementing SAP R/3 in a complicated manufacturing business. It provided a solid and concise understanding of the process of installing a SAP system to the average novice reader. This book emphasizes that it's not that simple to implement and integrate resources of an entire manufacturing process into one system. It involves lots of planning, patience, and asking the right questions on whether if SAP is right for your firm. Although I think this book was detailed enough to understand the outlying mechanics of ERP, I think that my ability to comprehend was delayed due to some of the technical jargon. This book would be helpful for experienced information systems administrators, but not for the average everyday Joe. It's like reading Japanese backwards!!! I would suggest to the authors of this book for it to be simplified even further to explain the details of ERP in way for the average reader to understand and absorb the basics of the system. In conclusion, if you're a manufacturing/operations geek...you will love this book!!!! =)

This actually is a good read. It kept my interest for a full 2 hours, which is what is took to read it. The case study is real and on the mark. It illustrates that even if SAP is being widely adopted in your industry (in this case furniture), it may not be the right solution for you. In this instance, SAP (or the SAP implementation approach) was wrong because the company, whose business model was "make to order", tried to cut time and costs by directly implementing a configuration which worked well for a company that has a very limited (few part numbers with minimal change) product line.

The author also did a realistic job in presenting the politics of the situation. The company president wanted an easy integration under a tight deadline. The IT geek wasn't interested in the business model and wanted a showcase quick installation. The marketing guy wasn't interested in the details and wanted to showcase the installation. The book's hero is a healthy skeptic, who is trying to understand ERP, its benefits, and how it fit his company's business.

Based the book's title, I thought I was picking up another SAP marketing book. But it is not that at all. It's objective and deals with business issues. No ABAP, idocs, and organization elements here.

This book contains lots of great pictures of web sites that have been completely re-designed since the writing of the book. Voila. If this is what you're looking for, then you'll be pleased with this book. However, if you're looking for more than that, look elsewhere. This book is a real disappiontment.

It seems that many of the more "flashy" designs described by Andres have given way to more usable designs that actually make sense to real people using / desiging sites today. While that book states that author has web design experience - it doesn't seem like he shares much of that with us. For example, the author will generally state that a particular site uses flash or uses animated gif's but give's little detail about how animated gif's could be best used in site design and site architecture.

The author spends most of his time criticizing sites and pointing out what he likes and doesn't like, which is fine. However, the author's tone is arrogant and self-absorbed. Additionally, the author ends chapters abrubptly, failing to guide the reader to the point that he might have been trying to make in that particular chapter. The only decent chapter in the book quite frankly is the chapter on hierarchical site organization (chapter one) and it's all downhill from there.

This is one of the worst books I've ever read on the subject of web design.

Since any designer wants to keep on top of what's going on in the industry, I thought it good to take a look at this book. I've gone from cover to cover a few times, but not to read it. After beginning I quickly realized the information is pretty basic and can pretty much be found by speaking with other's in the industry.

However, I did like some of the screenshots of various sites considered "great architecture." Often times, I flip through the book to generate a few ideas when putting together suggested views for sites in development.

In all, not much new information, but may be worth it if you're just starting out and just need to know or need information reinforced.

I've been reading all the rants about this book, and I only kind of disagree. It's certainly not about "Architecture" of web sites, as the name would have you believe. I bought it for its intended (but mis-named) purpose: I wanted to learn about UI and navigational considerations. It's an excellent book for that. It discusses solutions to different types of web site goals and how the site designers approached these challenges. One particularly useful example was Andres' evaluation of the (pre-redesign) Salon.com site. Andres considers each navigational element on the site (the home page's article layout, the bar navigation along the top, the related article information on the sides, and the base navigation along the bottom) and explains the reasoning behind each choice. Another example that specifically helped me in the design of my own website was the Braun/Gilette example. Andres discussed the virtues of having each sub-brand be in a page-style all its own.

Web UI books are difficult to write well, largely because the information is so timely and becomes outdated so quickly. The book has fantastic, full-color screenshots of each page in discussion so that, even if the page is no longer live on the web, it's still available for discussion.

It's probably the most valuable UI book on my shelves (and there are a lot). People who didn't like it had purchased it under the false pretense that it was an Architecture book. Well, it's *absolutely* not that. It's a Web UI Design book, and a really good one.